Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df02673d76109515ed8a607cb09d7827ba684c7bf060d1fb3a41daad9d514eb1

Tx prefix hash: 82c2f710b315b7ba15ec3fa0ed47f7525ed112c7347c119a63927bb3c1495e6f
Tx public key: 07e1361f3cdefd0d4b4e1cdbb1ed8d862fa7d89e6865a7e9f232734cb9ca042a
Timestamp: 1578231482 Timestamp [UCT]: 2020-01-05 13:38:02 Age [y:d:h:m:s]: 04:362:19:08:13
Block: 39214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148548 RingCT/type: yes/0
Extra: 0107e1361f3cdefd0d4b4e1cdbb1ed8d862fa7d89e6865a7e9f232734cb9ca042a02110000005d2264afe6000000000000000000

1 output(s) for total of 455.059922248000 dcy

stealth address amount amount idx
00: afa1ddb1e5a57447a8566aaf3051895dccaea0942e8c133bc09ae3cb747ba370 455.059922248000 67454 of 0

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": 39224, "vin": [ { "gen": { "height": 39214 } } ], "vout": [ { "amount": 455059922248, "target": { "key": "afa1ddb1e5a57447a8566aaf3051895dccaea0942e8c133bc09ae3cb747ba370" } } ], "extra": [ 1, 7, 225, 54, 31, 60, 222, 253, 13, 75, 78, 28, 219, 177, 237, 141, 134, 47, 167, 216, 158, 104, 101, 167, 233, 242, 50, 115, 76, 185, 202, 4, 42, 2, 17, 0, 0, 0, 93, 34, 100, 175, 230, 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