Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b058259fa2eee70bd451d51b23175342deb83592db9089aae48b5bfea3a37bb

Tx prefix hash: 3b4d5f0e536951f341d503d5c0825047e2ca253189a5b69300467205a0a56c8e
Tx public key: 5d312a47b7e4af7977680636a9259b0438678b7788ab9b5963e36df8d3596194
Timestamp: 1729582640 Timestamp [UCT]: 2024-10-22 07:37:20 Age [y:d:h:m:s]: 00:188:06:53:45
Block: 1136964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134399 RingCT/type: yes/0
Extra: 015d312a47b7e4af7977680636a9259b0438678b7788ab9b5963e36df8d3596194021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebcc5d2a931eb5d5d28e21e19c05495e3b07a53f004bb24623897b4a51fab2e4 0.600000000000 1620367 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": 1136974, "vin": [ { "gen": { "height": 1136964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebcc5d2a931eb5d5d28e21e19c05495e3b07a53f004bb24623897b4a51fab2e4" } } ], "extra": [ 1, 93, 49, 42, 71, 183, 228, 175, 121, 119, 104, 6, 54, 169, 37, 155, 4, 56, 103, 139, 119, 136, 171, 155, 89, 99, 227, 109, 248, 211, 89, 97, 148, 2, 17, 0, 0, 0, 4, 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