Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea99d5bbf0fea61e2dacf7f5c1ebddd45d5a029bda1c1ce677f7c6bf98fee0b8

Tx prefix hash: 07fe8350ae48eaf2c537d58fba45d36801b7ac9ae6252624b189cde440ae978f
Tx public key: f4b98cfb0d12709e7a464039cc8ac4844b1f268e64d0ba5c8c6e30558cfa52ad
Timestamp: 1728057654 Timestamp [UCT]: 2024-10-04 16:00:54 Age [y:d:h:m:s]: 00:108:15:36:35
Block: 1124373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77618 RingCT/type: yes/0
Extra: 01f4b98cfb0d12709e7a464039cc8ac4844b1f268e64d0ba5c8c6e30558cfa52ad02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53b4019cc8bee8e0764d599091d3b766a9867e1bfb2cc7cd1fab04c7b2579f4c 0.600000000000 1606990 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": 1124383, "vin": [ { "gen": { "height": 1124373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53b4019cc8bee8e0764d599091d3b766a9867e1bfb2cc7cd1fab04c7b2579f4c" } } ], "extra": [ 1, 244, 185, 140, 251, 13, 18, 112, 158, 122, 70, 64, 57, 204, 138, 196, 132, 75, 31, 38, 142, 100, 208, 186, 92, 140, 110, 48, 85, 140, 250, 82, 173, 2, 17, 0, 0, 0, 7, 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