Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d838aad12ca87374d53c769acdf612cff8656de8c3959a47aa596c6edfe7ef9

Tx prefix hash: b8ffa078285b9c5fe661bfdacfb1bcb7893e63266de570871230e1532d6fe55a
Tx public key: 8803259ddb1d162f203e07edc8d71b0de0601e39f37c0f6d13d2a790d9b1d84d
Timestamp: 1737295057 Timestamp [UCT]: 2025-01-19 13:57:37 Age [y:d:h:m:s]: 00:337:17:54:52
Block: 1200748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238980 RingCT/type: yes/0
Extra: 018803259ddb1d162f203e07edc8d71b0de0601e39f37c0f6d13d2a790d9b1d84d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb2b41736840f9306732b76a03979ea931190a65387c6e60509f37327dae3f05 0.600000000000 1687393 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": 1200758, "vin": [ { "gen": { "height": 1200748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb2b41736840f9306732b76a03979ea931190a65387c6e60509f37327dae3f05" } } ], "extra": [ 1, 136, 3, 37, 157, 219, 29, 22, 47, 32, 62, 7, 237, 200, 215, 27, 13, 224, 96, 30, 57, 243, 124, 15, 109, 19, 210, 167, 144, 217, 177, 216, 77, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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