Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e78cd889b5d2a9f20930b3b3f948da547b194acc5a88793a7938aadfb00ca1c3

Tx prefix hash: a26eea2293e4f11f14fe6d1606f766870d1993d129bd136964fa1c0b841bf4e1
Tx public key: 076f609ba3fd49dca77f9e6d16d1ddc8412eb34285ce57f03eb4b541cfbfa1ca
Timestamp: 1713043732 Timestamp [UCT]: 2024-04-13 21:28:52 Age [y:d:h:m:s]: 01:064:18:52:41
Block: 999866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307196 RingCT/type: yes/0
Extra: 01076f609ba3fd49dca77f9e6d16d1ddc8412eb34285ce57f03eb4b541cfbfa1ca02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbe4be523d039d30b313cecdf5edfed2c56f04ef22d9ef8d480a9c03fa03bd01 0.600000000000 1460354 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": 999876, "vin": [ { "gen": { "height": 999866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbe4be523d039d30b313cecdf5edfed2c56f04ef22d9ef8d480a9c03fa03bd01" } } ], "extra": [ 1, 7, 111, 96, 155, 163, 253, 73, 220, 167, 127, 158, 109, 22, 209, 221, 200, 65, 46, 179, 66, 133, 206, 87, 240, 62, 180, 181, 65, 207, 191, 161, 202, 2, 17, 0, 0, 0, 5, 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