Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 273334a3cc2afe956cbcd567da3e17921efad7afb402f1e98db559c9ce948f49

Tx prefix hash: 7ed39aadb5c73a4bba2d147be2a4c0470f8d66ed6979d176357b02721bae6223
Tx public key: 4004434e5ceab1de3136dbfd2087024fd1e6736e1e7e27c80653a89fd09f2a8b
Timestamp: 1704260897 Timestamp [UCT]: 2024-01-03 05:48:17 Age [y:d:h:m:s]: 01:311:14:08:49
Block: 927059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481533 RingCT/type: yes/0
Extra: 014004434e5ceab1de3136dbfd2087024fd1e6736e1e7e27c80653a89fd09f2a8b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 070b8836439d49d60c9ad8932dd9543e6f2aafff53fac70c3cd620358cbf8ec8 0.600000000000 1384859 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": 927069, "vin": [ { "gen": { "height": 927059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "070b8836439d49d60c9ad8932dd9543e6f2aafff53fac70c3cd620358cbf8ec8" } } ], "extra": [ 1, 64, 4, 67, 78, 92, 234, 177, 222, 49, 54, 219, 253, 32, 135, 2, 79, 209, 230, 115, 110, 30, 126, 39, 200, 6, 83, 168, 159, 208, 159, 42, 139, 2, 17, 0, 0, 0, 1, 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