Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7bc5437ca1010131d43c87ced68b5e3382ab10dfe0444d6eecfdec50d2911c4

Tx prefix hash: 054f7e8764f61cb1fcea63b5130ec9e0be2b93256be3abb43b5c14be6b8084e0
Tx public key: b2453f910fe4f95f33a4a6c144dfca51649d31d8018644ef98f2475689bd5f9e
Timestamp: 1712626544 Timestamp [UCT]: 2024-04-09 01:35:44 Age [y:d:h:m:s]: 00:267:11:56:37
Block: 996397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191509 RingCT/type: yes/0
Extra: 01b2453f910fe4f95f33a4a6c144dfca51649d31d8018644ef98f2475689bd5f9e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bc033161cc6c12d866b7f9e1d34faef76dcc8933718c5d2e3c9f1f2c43e3ddc 0.600000000000 1456815 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": 996407, "vin": [ { "gen": { "height": 996397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bc033161cc6c12d866b7f9e1d34faef76dcc8933718c5d2e3c9f1f2c43e3ddc" } } ], "extra": [ 1, 178, 69, 63, 145, 15, 228, 249, 95, 51, 164, 166, 193, 68, 223, 202, 81, 100, 157, 49, 216, 1, 134, 68, 239, 152, 242, 71, 86, 137, 189, 95, 158, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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