Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e6066f146a79e5a19cf59128e2e602ea3472e78e7c5f4d14a602a4681c16b2

Tx prefix hash: bb7edc33a38176eb70d6232eb8b73c1df865e0efc2904022eceb06189a6f066f
Tx public key: 9c878846550a55e08bb198033000cc93823b75040211c25d9930a8a09a8dc27d
Timestamp: 1710959556 Timestamp [UCT]: 2024-03-20 18:32:36 Age [y:d:h:m:s]: 00:315:12:40:06
Block: 982625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225575 RingCT/type: yes/0
Extra: 019c878846550a55e08bb198033000cc93823b75040211c25d9930a8a09a8dc27d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 740b1220a1160af7f7f67cb9e4e1165a86e0de519d041405f0217dd6893e2a9f 0.600000000000 1442734 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": 982635, "vin": [ { "gen": { "height": 982625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "740b1220a1160af7f7f67cb9e4e1165a86e0de519d041405f0217dd6893e2a9f" } } ], "extra": [ 1, 156, 135, 136, 70, 85, 10, 85, 224, 139, 177, 152, 3, 48, 0, 204, 147, 130, 59, 117, 4, 2, 17, 194, 93, 153, 48, 168, 160, 154, 141, 194, 125, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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