Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0373a8b2e344251e2d96fe9c457a7c43659fb83372673f7ddc5f03a41593f17f

Tx prefix hash: 978450a52cd71d40627eca11e21931addc268d98e3fd4859e14e1688a0652a8b
Tx public key: 99efb9978cd381f1749deb617a65dbdcb9dc141e5f9cb8296f6b6833427ad57c
Timestamp: 1734928323 Timestamp [UCT]: 2024-12-23 04:32:03 Age [y:d:h:m:s]: 00:112:13:20:46
Block: 1181230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80215 RingCT/type: yes/0
Extra: 0199efb9978cd381f1749deb617a65dbdcb9dc141e5f9cb8296f6b6833427ad57c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c935238854ee3ebb8d1eb51f64b942f820f7514fc78b88ce1b921c331929efb0 0.600000000000 1667647 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": 1181240, "vin": [ { "gen": { "height": 1181230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c935238854ee3ebb8d1eb51f64b942f820f7514fc78b88ce1b921c331929efb0" } } ], "extra": [ 1, 153, 239, 185, 151, 140, 211, 129, 241, 116, 157, 235, 97, 122, 101, 219, 220, 185, 220, 20, 30, 95, 156, 184, 41, 111, 107, 104, 51, 66, 122, 213, 124, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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