Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4102391cc3a106b8aab5cba9dc025e768e77f3ea0cbae7c7410b913889475e7

Tx prefix hash: d405056807d944a8a941139576dfacb09ce117a1ca3b79d9101b20dd8f5a901c
Tx public key: a9164a53c6c5f4b5b95feb17a8e4e99b9c535f44be774b1d6dcdb68d5bfb8413
Timestamp: 1574092188 Timestamp [UCT]: 2019-11-18 15:49:48 Age [y:d:h:m:s]: 05:084:00:30:11
Block: 11666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1203235 RingCT/type: yes/0
Extra: 01a9164a53c6c5f4b5b95feb17a8e4e99b9c535f44be774b1d6dcdb68d5bfb841302110000000266a80d00000000000000000000

1 output(s) for total of 561.495898486000 dcy

stealth address amount amount idx
00: 86acf966e8abbc8eb79363a283a8c69d2d2db8153c2ceab878ab2568dac74e5f 561.495898486000 12743 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": 11676, "vin": [ { "gen": { "height": 11666 } } ], "vout": [ { "amount": 561495898486, "target": { "key": "86acf966e8abbc8eb79363a283a8c69d2d2db8153c2ceab878ab2568dac74e5f" } } ], "extra": [ 1, 169, 22, 74, 83, 198, 197, 244, 181, 185, 95, 235, 23, 168, 228, 233, 155, 156, 83, 95, 68, 190, 119, 75, 29, 109, 205, 182, 141, 91, 251, 132, 19, 2, 17, 0, 0, 0, 2, 102, 168, 13, 0, 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