Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf62c19da266259c512a59e10ac52cff2d40dee95e48a658b854761a1f41bad9

Tx prefix hash: d150efaa388c37f1a5d39b71a8e7b3ba2f474ddde0cb4df2ae9c02d2cb70b2da
Tx public key: 8b0964b11d60dda12ef37a2f911ce240c669b9fc0a722ac17eb31eb6f03cad3f
Timestamp: 1718542722 Timestamp [UCT]: 2024-06-16 12:58:42 Age [y:d:h:m:s]: 00:278:19:26:48
Block: 1045491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199216 RingCT/type: yes/0
Extra: 018b0964b11d60dda12ef37a2f911ce240c669b9fc0a722ac17eb31eb6f03cad3f02110000000136ea7c8b000000000000000000

1 output(s) for total of 0.607780000000 dcy

stealth address amount amount idx
00: f4348b8ca91fee7ae79248c299191c7fa06e4497067c000209984ba2a9967b07 0.607780000000 1515076 of 0

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": 1045501, "vin": [ { "gen": { "height": 1045491 } } ], "vout": [ { "amount": 607780000, "target": { "key": "f4348b8ca91fee7ae79248c299191c7fa06e4497067c000209984ba2a9967b07" } } ], "extra": [ 1, 139, 9, 100, 177, 29, 96, 221, 161, 46, 243, 122, 47, 145, 28, 226, 64, 198, 105, 185, 252, 10, 114, 42, 193, 126, 179, 30, 182, 240, 60, 173, 63, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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