Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f01b827b0643cb0b457b7aeef6165947edf3af3734ff60eb75d8e8793c1d3a

Tx prefix hash: 850299d21a5d813f7ab81e7b4d8a8568257eb20476250cfdd609dbbc256ee404
Tx public key: 96d6ffb3100785cb5ed9c111af726abf2ff5fb8db1eb6a408253eaf762128da3
Timestamp: 1702017858 Timestamp [UCT]: 2023-12-08 06:44:18 Age [y:d:h:m:s]: 01:187:03:58:04
Block: 908478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394914 RingCT/type: yes/0
Extra: 0196d6ffb3100785cb5ed9c111af726abf2ff5fb8db1eb6a408253eaf762128da3021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e070916a71eae1ae1ca2d6ae694e4a78e5defe248feea34cc0ac2f31e2151368 0.600000000000 1365511 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": 908488, "vin": [ { "gen": { "height": 908478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e070916a71eae1ae1ca2d6ae694e4a78e5defe248feea34cc0ac2f31e2151368" } } ], "extra": [ 1, 150, 214, 255, 179, 16, 7, 133, 203, 94, 217, 193, 17, 175, 114, 106, 191, 47, 245, 251, 141, 177, 235, 106, 64, 130, 83, 234, 247, 98, 18, 141, 163, 2, 17, 0, 0, 0, 6, 230, 210, 127, 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