Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1a7b4ca88ffc46c12dd0e7b64142e47035172c78042dbfca8cc31bbfa763bc5

Tx prefix hash: d8f4210f9cca7a90d19190556d68f85a845bcdec017108bc71152da470ef621d
Tx public key: 8e75e79d2b29fce7451493bf4d835b4c72472c5f31a79d6c6ca761250c33f737
Timestamp: 1702382021 Timestamp [UCT]: 2023-12-12 11:53:41 Age [y:d:h:m:s]: 01:360:17:33:43
Block: 911515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516685 RingCT/type: yes/0
Extra: 018e75e79d2b29fce7451493bf4d835b4c72472c5f31a79d6c6ca761250c33f737021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7daf83e59821d771c0b20d3f03e6719f0d8b9d3e126f341e4309f7b7181d09da 0.600000000000 1368719 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": 911525, "vin": [ { "gen": { "height": 911515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7daf83e59821d771c0b20d3f03e6719f0d8b9d3e126f341e4309f7b7181d09da" } } ], "extra": [ 1, 142, 117, 231, 157, 43, 41, 252, 231, 69, 20, 147, 191, 77, 131, 91, 76, 114, 71, 44, 95, 49, 167, 157, 108, 108, 167, 97, 37, 12, 51, 247, 55, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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