Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18612384c2e728c05f433320122b297a4fe112061b6ed46f9dfd4f9afd4d6f67

Tx prefix hash: 4b37182a70c7f03e83ac8d89d620d08eeca77646d392144b09ca251e99df5e9e
Tx public key: 80ca389dcc0d6535d4375a7dc358f6527202aeb287909f70a6cac058f4fa52b9
Timestamp: 1702687370 Timestamp [UCT]: 2023-12-16 00:42:50 Age [y:d:h:m:s]: 01:035:10:46:26
Block: 914019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286661 RingCT/type: yes/0
Extra: 0180ca389dcc0d6535d4375a7dc358f6527202aeb287909f70a6cac058f4fa52b902110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3ad54e77a6298d20f045da548954ea81a436beda7cd1b66bd7c5cb5d8691754 0.600000000000 1371299 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": 914029, "vin": [ { "gen": { "height": 914019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3ad54e77a6298d20f045da548954ea81a436beda7cd1b66bd7c5cb5d8691754" } } ], "extra": [ 1, 128, 202, 56, 157, 204, 13, 101, 53, 212, 55, 90, 125, 195, 88, 246, 82, 114, 2, 174, 178, 135, 144, 159, 112, 166, 202, 192, 88, 244, 250, 82, 185, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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