Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 554054f5664e2cf1e8dc255ce64895b21bab3d5a98bc37a18c9bffa84c011ece

Tx prefix hash: 144d186c534796b936eefd229ae24f9c31c8a9c9206e2642b721a48d84ab5673
Tx public key: efcfe4c8c83b0fc7a7e44fb038ae6430c93128989ac5ce7a4dd784bc1ba0ad5a
Timestamp: 1731880322 Timestamp [UCT]: 2024-11-17 21:52:02 Age [y:d:h:m:s]: 00:178:05:54:45
Block: 1155967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127224 RingCT/type: yes/0
Extra: 01efcfe4c8c83b0fc7a7e44fb038ae6430c93128989ac5ce7a4dd784bc1ba0ad5a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dc54fd25a30ff4845691cf1bee944b15998f35afee8086b22be82a529d4fc47 0.600000000000 1641586 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": 1155977, "vin": [ { "gen": { "height": 1155967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dc54fd25a30ff4845691cf1bee944b15998f35afee8086b22be82a529d4fc47" } } ], "extra": [ 1, 239, 207, 228, 200, 200, 59, 15, 199, 167, 228, 79, 176, 56, 174, 100, 48, 201, 49, 40, 152, 154, 197, 206, 122, 77, 215, 132, 188, 27, 160, 173, 90, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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