Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3013d97bdf18d2d3d23c2bbef8191adb30c97ef20a810a62e3ecf1e54a9a597

Tx prefix hash: 31f30278706907b8ebbcd29aa8013af9e4df476e6e41b6ee9c542c05fdc9d16c
Tx public key: 0a9c32ed736e0add02a5207ab895072528cd212fb8370887bb4b3654ab84de4b
Timestamp: 1668979032 Timestamp [UCT]: 2022-11-20 21:17:12 Age [y:d:h:m:s]: 02:000:16:02:31
Block: 635474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522364 RingCT/type: yes/0
Extra: 010a9c32ed736e0add02a5207ab895072528cd212fb8370887bb4b3654ab84de4b02110000000171bd5189000000000000000000

1 output(s) for total of 4.812944437000 dcy

stealth address amount amount idx
00: 33640e438d464ca88e61a524a27cbb3e9d09a1c6437b3977e024a5424e4cb94a 4.812944437000 1074744 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": 635484, "vin": [ { "gen": { "height": 635474 } } ], "vout": [ { "amount": 4812944437, "target": { "key": "33640e438d464ca88e61a524a27cbb3e9d09a1c6437b3977e024a5424e4cb94a" } } ], "extra": [ 1, 10, 156, 50, 237, 115, 110, 10, 221, 2, 165, 32, 122, 184, 149, 7, 37, 40, 205, 33, 47, 184, 55, 8, 135, 187, 75, 54, 84, 171, 132, 222, 75, 2, 17, 0, 0, 0, 1, 113, 189, 81, 137, 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