Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ffc083b6794c0e61cb37bc1b095ce4494124060903332d7c767aaed5d870de

Tx prefix hash: 7071c55317d5851ec6b732cbc6939908b5777ab1ebd74e82cd33c7c5ce49be4e
Tx public key: 0d546b0be47b62d26f89b6393e7d470f226bb17839e3922c2947ddfe8dc230f9
Timestamp: 1738405228 Timestamp [UCT]: 2025-02-01 10:20:28 Age [y:d:h:m:s]: 00:292:12:06:16
Block: 1209712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206818 RingCT/type: yes/0
Extra: 010d546b0be47b62d26f89b6393e7d470f226bb17839e3922c2947ddfe8dc230f9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b03eaed553e8e6453c18930df9e2dd259a8eea2f8ca533950a8c407b010c3335 0.600000000000 1696457 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": 1209722, "vin": [ { "gen": { "height": 1209712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b03eaed553e8e6453c18930df9e2dd259a8eea2f8ca533950a8c407b010c3335" } } ], "extra": [ 1, 13, 84, 107, 11, 228, 123, 98, 210, 111, 137, 182, 57, 62, 125, 71, 15, 34, 107, 177, 120, 57, 227, 146, 44, 41, 71, 221, 254, 141, 194, 48, 249, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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