Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0910a084b811bbc0862654604287f79bde34dcb7d800c69d6e2f5cff29e7eb11

Tx prefix hash: 07d9db25d6788e2e4bbf8f8fd11d9fa9301af23d9f2d4e4eb456341363b34dd1
Tx public key: 54415f6f50d6c5918759a80dd8bad31025e6c659f25a6f753e3b2e0f4ed64c99
Timestamp: 1640817981 Timestamp [UCT]: 2021-12-29 22:46:21 Age [y:d:h:m:s]: 03:075:17:07:11
Block: 406337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 832893 RingCT/type: yes/0
Extra: 0154415f6f50d6c5918759a80dd8bad31025e6c659f25a6f753e3b2e0f4ed64c99021100000001cda45b65000000000000000000

1 output(s) for total of 27.646940582000 dcy

stealth address amount amount idx
00: 1be8c3c5a90ac6d6a4628dc1ad79b544f9b42cf73149d770893c12808159e929 27.646940582000 807161 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": 406347, "vin": [ { "gen": { "height": 406337 } } ], "vout": [ { "amount": 27646940582, "target": { "key": "1be8c3c5a90ac6d6a4628dc1ad79b544f9b42cf73149d770893c12808159e929" } } ], "extra": [ 1, 84, 65, 95, 111, 80, 214, 197, 145, 135, 89, 168, 13, 216, 186, 211, 16, 37, 230, 198, 89, 242, 90, 111, 117, 62, 59, 46, 15, 78, 214, 76, 153, 2, 17, 0, 0, 0, 1, 205, 164, 91, 101, 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