Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7fc202e930ba8e09df9f4018e634904709b73f026daf00d06a73157f7f22d01

Tx prefix hash: 0fed6fa99541b2ee7da7f01e6ff744804cad66f49f4e8a116153388aae072d23
Tx public key: 4eed3f903d2645ae5d8b3c3197430af80850a88b48000da0a0400bb230b83f8b
Timestamp: 1711913490 Timestamp [UCT]: 2024-03-31 19:31:30 Age [y:d:h:m:s]: 01:043:13:50:28
Block: 990527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292124 RingCT/type: yes/0
Extra: 014eed3f903d2645ae5d8b3c3197430af80850a88b48000da0a0400bb230b83f8b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87053ab6c3f0df618a372c2efbd8c89d74743aba7e5a3a58f3075b09fc5aab01 0.600000000000 1450849 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": 990537, "vin": [ { "gen": { "height": 990527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87053ab6c3f0df618a372c2efbd8c89d74743aba7e5a3a58f3075b09fc5aab01" } } ], "extra": [ 1, 78, 237, 63, 144, 61, 38, 69, 174, 93, 139, 60, 49, 151, 67, 10, 248, 8, 80, 168, 139, 72, 0, 13, 160, 160, 64, 11, 178, 48, 184, 63, 139, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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