Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6aef4102c7963606ff5eb3cad26688a72f0dea747f1a6565b660769b167f98b

Tx prefix hash: ee1ae8fb14f95f494f80012e0edcec7fd67e6dd277d0ff4dfc39115d66441424
Tx public key: 5f3553f34e8487ab6712e942aa7d712c0fd965b2a960da8a617f4c78e3b71420
Timestamp: 1579109182 Timestamp [UCT]: 2020-01-15 17:26:22 Age [y:d:h:m:s]: 04:347:00:18:32
Block: 46193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137542 RingCT/type: yes/0
Extra: 015f3553f34e8487ab6712e942aa7d712c0fd965b2a960da8a617f4c78e3b714200211000000074ac5aa02000000000000000000

1 output(s) for total of 431.478590567000 dcy

stealth address amount amount idx
00: 9466a2eb584bea73b7f50cd92dc628d9fff65b2f5683a590e136e4f4ef7e4c7d 431.478590567000 84855 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": 46203, "vin": [ { "gen": { "height": 46193 } } ], "vout": [ { "amount": 431478590567, "target": { "key": "9466a2eb584bea73b7f50cd92dc628d9fff65b2f5683a590e136e4f4ef7e4c7d" } } ], "extra": [ 1, 95, 53, 83, 243, 78, 132, 135, 171, 103, 18, 233, 66, 170, 125, 113, 44, 15, 217, 101, 178, 169, 96, 218, 138, 97, 127, 76, 120, 227, 183, 20, 32, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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