Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5dffd690087f96c41f878997779f7e03d9ad30e7ba432c77cec783aa2a7dfa

Tx prefix hash: 7a4f18b5282ddfc92aa7ee193a443a9f5056e516ce77a4861b0588a9d813a090
Tx public key: e370cfab03fb36330a7ed42a5dbe0924f39e9416b75e0282ac631b23f09cc976
Timestamp: 1737610713 Timestamp [UCT]: 2025-01-23 05:38:33 Age [y:d:h:m:s]: 00:053:07:03:33
Block: 1203363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37914 RingCT/type: yes/0
Extra: 01e370cfab03fb36330a7ed42a5dbe0924f39e9416b75e0282ac631b23f09cc976021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ce98f32af868dc9236a9edb2b0d3f68620c4eb167e593ef592a04cb258aa051 0.600000000000 1690040 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": 1203373, "vin": [ { "gen": { "height": 1203363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ce98f32af868dc9236a9edb2b0d3f68620c4eb167e593ef592a04cb258aa051" } } ], "extra": [ 1, 227, 112, 207, 171, 3, 251, 54, 51, 10, 126, 212, 42, 93, 190, 9, 36, 243, 158, 148, 22, 183, 94, 2, 130, 172, 99, 27, 35, 240, 156, 201, 118, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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