Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de40490b521211a104a2b47924643f3c04743ff86a3b3c585c768de833baffc0

Tx prefix hash: 4ff8049915950ff96366584e2f724d83978c532cac3ed6f9f2893a9fd36829c9
Tx public key: 15701fe0b6efa223f8b29e4c34a1930e09c00f2bf9655af291fafb9cd825989b
Timestamp: 1719068433 Timestamp [UCT]: 2024-06-22 15:00:33 Age [y:d:h:m:s]: 00:358:08:42:54
Block: 1049815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256045 RingCT/type: yes/0
Extra: 0115701fe0b6efa223f8b29e4c34a1930e09c00f2bf9655af291fafb9cd825989b02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb6f8282857fa5d915fad9d738c60dfad1bb4ec4688f78d4746a8bb6e5244a80 0.600000000000 1519920 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": 1049825, "vin": [ { "gen": { "height": 1049815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb6f8282857fa5d915fad9d738c60dfad1bb4ec4688f78d4746a8bb6e5244a80" } } ], "extra": [ 1, 21, 112, 31, 224, 182, 239, 162, 35, 248, 178, 158, 76, 52, 161, 147, 14, 9, 192, 15, 43, 249, 101, 90, 242, 145, 250, 251, 156, 216, 37, 152, 155, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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