Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e960319ec4dfd8b965b8cc4128cbafc7bdd67a1e5b79966ba1f0ea0d077562b

Tx prefix hash: e414a7f8e0b8a9711bc8d05ef4c60cf0016fa163a77a45a942ac21197926f480
Tx public key: 3796fc3d1352ae5bb470c35c96363caf16a7043621f45c8016d4b63add3010ef
Timestamp: 1724905562 Timestamp [UCT]: 2024-08-29 04:26:02 Age [y:d:h:m:s]: 00:055:16:15:02
Block: 1098219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39861 RingCT/type: yes/0
Extra: 013796fc3d1352ae5bb470c35c96363caf16a7043621f45c8016d4b63add3010ef02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88a1b57b7bc01cdb191d2a286a1be1487b699e52fb089904c6307d24da469dfe 0.600000000000 1573862 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": 1098229, "vin": [ { "gen": { "height": 1098219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88a1b57b7bc01cdb191d2a286a1be1487b699e52fb089904c6307d24da469dfe" } } ], "extra": [ 1, 55, 150, 252, 61, 19, 82, 174, 91, 180, 112, 195, 92, 150, 54, 60, 175, 22, 167, 4, 54, 33, 244, 92, 128, 22, 212, 182, 58, 221, 48, 16, 239, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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