Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353ccf52406353dfe0cb873012e011ed47d7bf5d4f5d1e6b05d329d457ccbf9e

Tx prefix hash: b9f100d6ce31fd1f6566a44828f8640e85029eee2330097203393e8fb9abc95e
Tx public key: 917e9c38d1957bbacb185d7f946356cc512aebc4df42edc54cc349903a05e77a
Timestamp: 1701622151 Timestamp [UCT]: 2023-12-03 16:49:11 Age [y:d:h:m:s]: 01:047:16:17:52
Block: 905196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295416 RingCT/type: yes/0
Extra: 01917e9c38d1957bbacb185d7f946356cc512aebc4df42edc54cc349903a05e77a021100000001faf35c9c000000000000000000

1 output(s) for total of 0.614766032000 dcy

stealth address amount amount idx
00: 017732cd607969d64bbb0bec38176f54c8ea0b799d2ba57388c284c264fb323b 0.614766032000 1362071 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": 905206, "vin": [ { "gen": { "height": 905196 } } ], "vout": [ { "amount": 614766032, "target": { "key": "017732cd607969d64bbb0bec38176f54c8ea0b799d2ba57388c284c264fb323b" } } ], "extra": [ 1, 145, 126, 156, 56, 209, 149, 123, 186, 203, 24, 93, 127, 148, 99, 86, 204, 81, 42, 235, 196, 223, 66, 237, 197, 76, 195, 73, 144, 58, 5, 231, 122, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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