Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1084c57c1afebc84b3de5b2d249d6e94bc8970b62cb17a7c5b04f105fd192c41

Tx prefix hash: 2336d575f8c1afcd257a3d705158effbda263268970a0bda70aa715aadcca2d2
Tx public key: dc6af494f8eb707be5af82d41dadebe6f41e2829d5ceb2b6cb753c7a86270ad2
Timestamp: 1647502768 Timestamp [UCT]: 2022-03-17 07:39:28 Age [y:d:h:m:s]: 03:229:08:43:48
Block: 460235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 941812 RingCT/type: yes/0
Extra: 01dc6af494f8eb707be5af82d41dadebe6f41e2829d5ceb2b6cb753c7a86270ad2021100000001cb8520c2000000000000000000

1 output(s) for total of 18.325281561000 dcy

stealth address amount amount idx
00: 9ce420770f3290036ac939dd364243b27abf69b29f56dd17a62df841ab432147 18.325281561000 877164 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": 460245, "vin": [ { "gen": { "height": 460235 } } ], "vout": [ { "amount": 18325281561, "target": { "key": "9ce420770f3290036ac939dd364243b27abf69b29f56dd17a62df841ab432147" } } ], "extra": [ 1, 220, 106, 244, 148, 248, 235, 112, 123, 229, 175, 130, 212, 29, 173, 235, 230, 244, 30, 40, 41, 213, 206, 178, 182, 203, 117, 60, 122, 134, 39, 10, 210, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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