Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8d8b8deb89488e9b296c7c6428e9a25ecd9fa675740249fc39ee4f20b9ae3d7

Tx prefix hash: 2eecbdb0934cfaddaa4697c11bfdf1183958bdf5989a9353c82c00885b9d7164
Tx public key: 76025c2185cad3db1df42daf49c96b24929b72357e396b9298a30bd1f885874c
Timestamp: 1734315433 Timestamp [UCT]: 2024-12-16 02:17:13 Age [y:d:h:m:s]: 00:185:14:13:05
Block: 1176145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132336 RingCT/type: yes/0
Extra: 0176025c2185cad3db1df42daf49c96b24929b72357e396b9298a30bd1f885874c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9d6aa8e77bd23eaf5fec12f0c2efa7b318b1dc6ba507bceddf35e1626ca68c1 0.600000000000 1662476 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": 1176155, "vin": [ { "gen": { "height": 1176145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9d6aa8e77bd23eaf5fec12f0c2efa7b318b1dc6ba507bceddf35e1626ca68c1" } } ], "extra": [ 1, 118, 2, 92, 33, 133, 202, 211, 219, 29, 244, 45, 175, 73, 201, 107, 36, 146, 155, 114, 53, 126, 57, 107, 146, 152, 163, 11, 209, 248, 133, 135, 76, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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