Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320da9016e19226c4cac7c5bddb5727b8b84c4d8a22c0ee2e280737402c88809

Tx prefix hash: e70c41d07dbdd29064e21c4ddd8a047ca22bb4bd84f80cbad8f3197699abc77a
Tx public key: 70611733b968f4d8288aa10b52ad69d807fab2315129780d2610585f6dd6c0e2
Timestamp: 1705876903 Timestamp [UCT]: 2024-01-21 22:41:43 Age [y:d:h:m:s]: 01:087:07:19:01
Block: 940438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323511 RingCT/type: yes/0
Extra: 0170611733b968f4d8288aa10b52ad69d807fab2315129780d2610585f6dd6c0e20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73b7930b172a46a77cfb7e84f4ecc210e7a50def2f8ff78e627c7b48069b9a02 0.600000000000 1398576 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": 940448, "vin": [ { "gen": { "height": 940438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73b7930b172a46a77cfb7e84f4ecc210e7a50def2f8ff78e627c7b48069b9a02" } } ], "extra": [ 1, 112, 97, 23, 51, 185, 104, 244, 216, 40, 138, 161, 11, 82, 173, 105, 216, 7, 250, 178, 49, 81, 41, 120, 13, 38, 16, 88, 95, 109, 214, 192, 226, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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