Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 800566d4b43180d0425d6fb5322254bf3c25c4516d7813cc74248f97a92bdcee

Tx prefix hash: 3583770c5a4a64d04b3dd7c3f41f3c05bc622b7d72bb4a62b3783a1b9f9df9ee
Tx public key: 01158799df7f7402c1497ad40104cd29a07ed7af6d64b3f8a8ed750094aed7ae
Timestamp: 1715527463 Timestamp [UCT]: 2024-05-12 15:24:23 Age [y:d:h:m:s]: 01:004:05:08:47
Block: 1020513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263895 RingCT/type: yes/0
Extra: 0101158799df7f7402c1497ad40104cd29a07ed7af6d64b3f8a8ed750094aed7ae02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38fb7dae24117e0ec3621cba48d69703996a4f0d5f5007c68f209667936cdbdc 0.600000000000 1484590 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": 1020523, "vin": [ { "gen": { "height": 1020513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38fb7dae24117e0ec3621cba48d69703996a4f0d5f5007c68f209667936cdbdc" } } ], "extra": [ 1, 1, 21, 135, 153, 223, 127, 116, 2, 193, 73, 122, 212, 1, 4, 205, 41, 160, 126, 215, 175, 109, 100, 179, 248, 168, 237, 117, 0, 148, 174, 215, 174, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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