Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 910e44002eb3c515b122674b748091a8e457f5482bacdf643d018c2343777ce5

Tx prefix hash: 2ed19c2ce63f7d2afa27b1decd4a507b3ab22bb6156ab215a39e0cb77fcfe4e1
Tx public key: 1e765a44cf39be346d1fa1df25da10d7dec1f1ad3326441acc4f348c7a65a00d
Timestamp: 1728939105 Timestamp [UCT]: 2024-10-14 20:51:45 Age [y:d:h:m:s]: 00:247:12:08:12
Block: 1131668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176575 RingCT/type: yes/0
Extra: 011e765a44cf39be346d1fa1df25da10d7dec1f1ad3326441acc4f348c7a65a00d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ec2e61ab61576603e1e9e8bdf68d5d37095293e685e2c332ea51568134682dc 0.600000000000 1614571 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1131678, "vin": [ { "gen": { "height": 1131668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ec2e61ab61576603e1e9e8bdf68d5d37095293e685e2c332ea51568134682dc" } } ], "extra": [ 1, 30, 118, 90, 68, 207, 57, 190, 52, 109, 31, 161, 223, 37, 218, 16, 215, 222, 193, 241, 173, 51, 38, 68, 26, 204, 79, 52, 140, 122, 101, 160, 13, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8