Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820b72e043785327bc4ff23e79fa4e1236e8377e8fb04cfc41bd8c30d9b818e6

Tx prefix hash: b70a3694fa17bda93d3be6b057f3f8a6130b987dac753defd5e5133c3927ae38
Tx public key: 9ca174822ac093644f43577f240c3ec6a2e5ea6a143f4883f5325c7969241ea2
Timestamp: 1578552934 Timestamp [UCT]: 2020-01-09 06:55:34 Age [y:d:h:m:s]: 05:300:22:51:18
Block: 41833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1362748 RingCT/type: yes/0
Extra: 019ca174822ac093644f43577f240c3ec6a2e5ea6a143f4883f5325c7969241ea202110000000f17786bcf000000000000000000

1 output(s) for total of 446.057401667000 dcy

stealth address amount amount idx
00: 37d7de70a86c5d7bd9fd15f4dcfcf1a111d506a1318adf0428c1a6d32287dfd9 446.057401667000 74966 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": 41843, "vin": [ { "gen": { "height": 41833 } } ], "vout": [ { "amount": 446057401667, "target": { "key": "37d7de70a86c5d7bd9fd15f4dcfcf1a111d506a1318adf0428c1a6d32287dfd9" } } ], "extra": [ 1, 156, 161, 116, 130, 42, 192, 147, 100, 79, 67, 87, 127, 36, 12, 62, 198, 162, 229, 234, 106, 20, 63, 72, 131, 245, 50, 92, 121, 105, 36, 30, 162, 2, 17, 0, 0, 0, 15, 23, 120, 107, 207, 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