Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce4beb96493d349e664348e70d68b4bf0a4fd9ca1c7f14721ac64758e543c7b

Tx prefix hash: 361134900d32660623fa708c32680764d2be0430a3af18677b980e52cac0ea31
Tx public key: 9e6cb5e12d80031023cb5adcd259807779a4c0c0f3eccda8bb1c3a33c67b83ba
Timestamp: 1577885377 Timestamp [UCT]: 2020-01-01 13:29:37 Age [y:d:h:m:s]: 05:108:23:09:42
Block: 36356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227792 RingCT/type: yes/0
Extra: 019e6cb5e12d80031023cb5adcd259807779a4c0c0f3eccda8bb1c3a33c67b83ba02110000001dac34bf9e000000000000000000

1 output(s) for total of 465.091425517000 dcy

stealth address amount amount idx
00: de78063d6d61c3d65bd502f76c7a9456dae85db80ca860dcc73a3694f3236ceb 465.091425517000 61563 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": 36366, "vin": [ { "gen": { "height": 36356 } } ], "vout": [ { "amount": 465091425517, "target": { "key": "de78063d6d61c3d65bd502f76c7a9456dae85db80ca860dcc73a3694f3236ceb" } } ], "extra": [ 1, 158, 108, 181, 225, 45, 128, 3, 16, 35, 203, 90, 220, 210, 89, 128, 119, 121, 164, 192, 192, 243, 236, 205, 168, 187, 28, 58, 51, 198, 123, 131, 186, 2, 17, 0, 0, 0, 29, 172, 52, 191, 158, 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