Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf600fcc850548ab737a135b4dffae0d16f0bca9e064cf9963a4e84f84fab3e4

Tx prefix hash: 74450626cfc1e0c8776dfc5521adfe4e1818c844a5241edfb7cf0ba4b02dcc30
Tx public key: fd1729a682bbcc422cc1a0cce776d7bcf12a68fee2b8a62d9d04bd9e69f61c98
Timestamp: 1716221315 Timestamp [UCT]: 2024-05-20 16:08:35 Age [y:d:h:m:s]: 01:028:00:11:26
Block: 1026233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280827 RingCT/type: yes/0
Extra: 01fd1729a682bbcc422cc1a0cce776d7bcf12a68fee2b8a62d9d04bd9e69f61c9802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b46d4a2b20f24aa449ae94f6f8475489013242fb2086909e265babfb063fa11 0.600000000000 1493202 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": 1026243, "vin": [ { "gen": { "height": 1026233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b46d4a2b20f24aa449ae94f6f8475489013242fb2086909e265babfb063fa11" } } ], "extra": [ 1, 253, 23, 41, 166, 130, 187, 204, 66, 44, 193, 160, 204, 231, 118, 215, 188, 241, 42, 104, 254, 226, 184, 166, 45, 157, 4, 189, 158, 105, 246, 28, 152, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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