Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f225972554eff2130cf4949f55436f1c97aa4fd205a2f611299fe728033ee959

Tx prefix hash: 965afad5e97b5aa41ceab951ca6f1e9d330fcacb8228add1218493a41ceb10f2
Tx public key: e2ce6f0e8b2eadb4d17029331d2805d9b8625d295c7e83a904960c476310837a
Timestamp: 1712614963 Timestamp [UCT]: 2024-04-08 22:22:43 Age [y:d:h:m:s]: 01:053:16:49:32
Block: 996305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299401 RingCT/type: yes/0
Extra: 01e2ce6f0e8b2eadb4d17029331d2805d9b8625d295c7e83a904960c476310837a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbc9f4f24b8312eb8d6d126a05774cbe12fba45e7211b78c144ca1e4ee9716ed 0.600000000000 1456723 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": 996315, "vin": [ { "gen": { "height": 996305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbc9f4f24b8312eb8d6d126a05774cbe12fba45e7211b78c144ca1e4ee9716ed" } } ], "extra": [ 1, 226, 206, 111, 14, 139, 46, 173, 180, 209, 112, 41, 51, 29, 40, 5, 217, 184, 98, 93, 41, 92, 126, 131, 169, 4, 150, 12, 71, 99, 16, 131, 122, 2, 17, 0, 0, 0, 1, 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