Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a95517a21ab6d5f52f108cbdb503842a57503c73781fc27c1e92a6da7dd980d4

Tx prefix hash: ed859023dc092bb8e7ec5488799a498d1dbff0fabd92e42e4ea7c3ad3a82ad11
Tx public key: 6745b95916d4284b75cb39fe39960a613a5650c20f8a8b689e63849fe14db329
Timestamp: 1577644758 Timestamp [UCT]: 2019-12-29 18:39:18 Age [y:d:h:m:s]: 05:009:10:11:07
Block: 34485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156747 RingCT/type: yes/0
Extra: 016745b95916d4284b75cb39fe39960a613a5650c20f8a8b689e63849fe14db329021100000004d81c26c0000000000000000000

1 output(s) for total of 471.866544698000 dcy

stealth address amount amount idx
00: b90c10ac919546278f0208ecc0faf043da3b7e493982542cb985e03cac211aa1 471.866544698000 58035 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": 34495, "vin": [ { "gen": { "height": 34485 } } ], "vout": [ { "amount": 471866544698, "target": { "key": "b90c10ac919546278f0208ecc0faf043da3b7e493982542cb985e03cac211aa1" } } ], "extra": [ 1, 103, 69, 185, 89, 22, 212, 40, 75, 117, 203, 57, 254, 57, 150, 10, 97, 58, 86, 80, 194, 15, 138, 139, 104, 158, 99, 132, 159, 225, 77, 179, 41, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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