Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335076c0720adb6d9014315cefef5e1543cf3dc2331c64fab91edb6db3abfa84

Tx prefix hash: bd6764fc8a0543d4b3ce2231e692d11dc80c5670f27d2ad560f860f30a93e7e3
Tx public key: f882e8ddbc2b04650692426f30dda142dca295f0827765eec769b806b8b85610
Timestamp: 1703443704 Timestamp [UCT]: 2023-12-24 18:48:24 Age [y:d:h:m:s]: 01:322:02:45:58
Block: 920298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489053 RingCT/type: yes/0
Extra: 01f882e8ddbc2b04650692426f30dda142dca295f0827765eec769b806b8b8561002110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8847aa2edb3896423b0bfbfe4e825b38c27128502b4a2f4fcab19ef095c4ba58 0.600000000000 1377976 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": 920308, "vin": [ { "gen": { "height": 920298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8847aa2edb3896423b0bfbfe4e825b38c27128502b4a2f4fcab19ef095c4ba58" } } ], "extra": [ 1, 248, 130, 232, 221, 188, 43, 4, 101, 6, 146, 66, 111, 48, 221, 161, 66, 220, 162, 149, 240, 130, 119, 101, 238, 199, 105, 184, 6, 184, 184, 86, 16, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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