Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e676c96f5080881e202fbd5db8f412f72a181c7c79f9b8349581fd12a83ddab

Tx prefix hash: 17fe9f662d98da805eb020e962c9239f0bfb7bff8a57c26ca4c61992c6357b32
Tx public key: f1a9e86da234b639d527e145048acdad2b59973e5ae9027c32fb927c545bacfe
Timestamp: 1705474304 Timestamp [UCT]: 2024-01-17 06:51:44 Age [y:d:h:m:s]: 01:145:12:14:46
Block: 937108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365143 RingCT/type: yes/0
Extra: 01f1a9e86da234b639d527e145048acdad2b59973e5ae9027c32fb927c545bacfe02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a0ed084d8dbde03b86d8ad9f6d31d7a0cc3740f1b0a605b43a4be4de567c55 0.600000000000 1395152 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": 937118, "vin": [ { "gen": { "height": 937108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a0ed084d8dbde03b86d8ad9f6d31d7a0cc3740f1b0a605b43a4be4de567c55" } } ], "extra": [ 1, 241, 169, 232, 109, 162, 52, 182, 57, 213, 39, 225, 69, 4, 138, 205, 173, 43, 89, 151, 62, 90, 233, 2, 124, 50, 251, 146, 124, 84, 91, 172, 254, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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