Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc7710d3d314772925f12f5afda0c8f8f1a245d516f039d26fda14629d4e8fa

Tx prefix hash: 8e2aa647578c49ad08afda161bad134b02cf83366514743d8c35dbbb90ecfd15
Tx public key: 21bbed47e6dd6d0bf09d53a1b2a5732387d69fb1fb545010c4ea69fa8554151a
Timestamp: 1710593817 Timestamp [UCT]: 2024-03-16 12:56:57 Age [y:d:h:m:s]: 00:343:17:41:20
Block: 979591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245725 RingCT/type: yes/0
Extra: 0121bbed47e6dd6d0bf09d53a1b2a5732387d69fb1fb545010c4ea69fa8554151a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6546b1993eedaef0b1a35b5d3720a52535c68c3c1e774ba152c2b42b4024b655 0.600000000000 1439628 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": 979601, "vin": [ { "gen": { "height": 979591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6546b1993eedaef0b1a35b5d3720a52535c68c3c1e774ba152c2b42b4024b655" } } ], "extra": [ 1, 33, 187, 237, 71, 230, 221, 109, 11, 240, 157, 83, 161, 178, 165, 115, 35, 135, 214, 159, 177, 251, 84, 80, 16, 196, 234, 105, 250, 133, 84, 21, 26, 2, 17, 0, 0, 0, 7, 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