Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38935c98b41fcb6f970f729158bb6f9b2e7c0263a4f810bb2a2dd7a085f3264f

Tx prefix hash: 79df849fe237618b712ac4087f93c48a1278c0eda85702ad365924ae66a8d329
Tx public key: 7efd865b09f9ba4d011ad92b081ab81250e4ca7f78e54a6b58916ba49ced7fe4
Timestamp: 1704731895 Timestamp [UCT]: 2024-01-08 16:38:15 Age [y:d:h:m:s]: 01:100:05:32:24
Block: 930964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332732 RingCT/type: yes/0
Extra: 017efd865b09f9ba4d011ad92b081ab81250e4ca7f78e54a6b58916ba49ced7fe402110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a76832f33050a5503c5fdc430f9772e35624086fbe74d5c21c2952d41862091c 0.600000000000 1388856 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": 930974, "vin": [ { "gen": { "height": 930964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a76832f33050a5503c5fdc430f9772e35624086fbe74d5c21c2952d41862091c" } } ], "extra": [ 1, 126, 253, 134, 91, 9, 249, 186, 77, 1, 26, 217, 43, 8, 26, 184, 18, 80, 228, 202, 127, 120, 229, 74, 107, 88, 145, 107, 164, 156, 237, 127, 228, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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