Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81cd87a01ba0e8c8213205df5ec29dff4236fc4cd844e5f268433b45cd353205

Tx prefix hash: 0dc17472499401f9922353071fa3995e2e62c58b7f174661db971e4a1a448875
Tx public key: e5306541b91725f79ad6a35ad270136ea0dfcbd43cb71a0f47f2c87968c0d717
Timestamp: 1703491580 Timestamp [UCT]: 2023-12-25 08:06:20 Age [y:d:h:m:s]: 01:176:10:30:23
Block: 920691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387136 RingCT/type: yes/0
Extra: 01e5306541b91725f79ad6a35ad270136ea0dfcbd43cb71a0f47f2c87968c0d71702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa2e04f54c8b93d58d6d6df7ff00056dc6c399c4ae00dd60bdb69741d86d099f 0.600000000000 1378373 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": 920701, "vin": [ { "gen": { "height": 920691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa2e04f54c8b93d58d6d6df7ff00056dc6c399c4ae00dd60bdb69741d86d099f" } } ], "extra": [ 1, 229, 48, 101, 65, 185, 23, 37, 247, 154, 214, 163, 90, 210, 112, 19, 110, 160, 223, 203, 212, 60, 183, 26, 15, 71, 242, 200, 121, 104, 192, 215, 23, 2, 17, 0, 0, 0, 3, 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