Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2c7781d24b8148088e7c87b3a63c208fde97d76b99f7229088b3963e970683

Tx prefix hash: 5cd329fe8353265028ce77eedd2c4a0f102e7abb11c2dc6c979fc2f4537ef27a
Tx public key: fcb79bab4c311ace209118432a7d1fb93c1502fee14e8ad3241c8291bf563e8a
Timestamp: 1728860347 Timestamp [UCT]: 2024-10-13 22:59:07 Age [y:d:h:m:s]: 01:026:13:15:59
Block: 1131011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277346 RingCT/type: yes/0
Extra: 01fcb79bab4c311ace209118432a7d1fb93c1502fee14e8ad3241c8291bf563e8a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 948bb9e590f75e74e2a65cd85ed5e63cef95a640b1e61654f93e721d1ae62ec4 0.600000000000 1613892 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": 1131021, "vin": [ { "gen": { "height": 1131011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "948bb9e590f75e74e2a65cd85ed5e63cef95a640b1e61654f93e721d1ae62ec4" } } ], "extra": [ 1, 252, 183, 155, 171, 76, 49, 26, 206, 32, 145, 24, 67, 42, 125, 31, 185, 60, 21, 2, 254, 225, 78, 138, 211, 36, 28, 130, 145, 191, 86, 62, 138, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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