Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a87e3a7dc831ad9bc19638c579141810dbb185681e642b2aee79532cc361d3b

Tx prefix hash: d287f7b16dc4f81856046906d24a7cfae998a94774645eac9b01e70ba55b069c
Tx public key: 878deab9146ef3c01d6a1c67b55cc346d4650f722581fe096ca8a1e758c789bc
Timestamp: 1727676676 Timestamp [UCT]: 2024-09-30 06:11:16 Age [y:d:h:m:s]: 00:176:05:15:54
Block: 1121196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125741 RingCT/type: yes/0
Extra: 01878deab9146ef3c01d6a1c67b55cc346d4650f722581fe096ca8a1e758c789bc02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0300e96edbd1d119d7fb436ad741c136a512ad34a106cfe1704c66c8d4dc25c 0.600000000000 1603387 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": 1121206, "vin": [ { "gen": { "height": 1121196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0300e96edbd1d119d7fb436ad741c136a512ad34a106cfe1704c66c8d4dc25c" } } ], "extra": [ 1, 135, 141, 234, 185, 20, 110, 243, 192, 29, 106, 28, 103, 181, 92, 195, 70, 212, 101, 15, 114, 37, 129, 254, 9, 108, 168, 161, 231, 88, 199, 137, 188, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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