Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b6040ee2cea35f8a9d0c3919277eb65474df4d8df3b9e401fa32e11d56ed43d

Tx prefix hash: 94aba1bbf8980cb0773dca92f4b8e851d8fe6d26e0601998da4ad303ef957117
Tx public key: 2f7637a646ea5014c9e6bcb67892a633534e001e06cf38db7f955c91d5bc8378
Timestamp: 1703600213 Timestamp [UCT]: 2023-12-26 14:16:53 Age [y:d:h:m:s]: 01:320:00:05:55
Block: 921591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487542 RingCT/type: yes/0
Extra: 012f7637a646ea5014c9e6bcb67892a633534e001e06cf38db7f955c91d5bc83780211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a1fd52e6558a5ed05f44dae528e4560b76e2ec1d8647dbc2d20c8fff502a7d2 0.600000000000 1379281 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": 921601, "vin": [ { "gen": { "height": 921591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a1fd52e6558a5ed05f44dae528e4560b76e2ec1d8647dbc2d20c8fff502a7d2" } } ], "extra": [ 1, 47, 118, 55, 166, 70, 234, 80, 20, 201, 230, 188, 182, 120, 146, 166, 51, 83, 78, 0, 30, 6, 207, 56, 219, 127, 149, 92, 145, 213, 188, 131, 120, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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