Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 576dbe72b38fe4178b499de96507cd80293e701983f0b3fea0d0c35d5f3baa7a

Tx prefix hash: 255b0342e0b9998e1c1e71efe7155c43b0506cb0bb08e9c3652db03bb80ae992
Tx public key: 57ae2bf21595cb844ffd8dc36785ff6a8473f20205038a549a5e7478d1443685
Timestamp: 1718689900 Timestamp [UCT]: 2024-06-18 05:51:40 Age [y:d:h:m:s]: 00:287:14:52:16
Block: 1046697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205516 RingCT/type: yes/0
Extra: 0157ae2bf21595cb844ffd8dc36785ff6a8473f20205038a549a5e7478d144368502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 433b15bd9d9ce4eae4b8402d702a7b1baa57a1821a87bd4eed123ae1849b8334 0.600000000000 1516514 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": 1046707, "vin": [ { "gen": { "height": 1046697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "433b15bd9d9ce4eae4b8402d702a7b1baa57a1821a87bd4eed123ae1849b8334" } } ], "extra": [ 1, 87, 174, 43, 242, 21, 149, 203, 132, 79, 253, 141, 195, 103, 133, 255, 106, 132, 115, 242, 2, 5, 3, 138, 84, 154, 94, 116, 120, 209, 68, 54, 133, 2, 17, 0, 0, 0, 3, 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