Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c5d36cb622e1e42aa28f7eec3084887f3838a2fdf17f6f817478f952b72a70

Tx prefix hash: 76b68e6d440f8c0caa91c2c59bbd881f3d6019c7ed90fdeff98a7c04007b0663
Tx public key: 83720193fe03683af04180776849b2d059274e2b81df6e7d27dbf0cfc54a429b
Timestamp: 1710599223 Timestamp [UCT]: 2024-03-16 14:27:03 Age [y:d:h:m:s]: 01:058:03:40:11
Block: 979634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302561 RingCT/type: yes/0
Extra: 0183720193fe03683af04180776849b2d059274e2b81df6e7d27dbf0cfc54a429b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fe6d3fd2003cb8740adc4c3dae035c42565d8bed590f1143cf941495f800db6 0.600000000000 1439677 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": 979644, "vin": [ { "gen": { "height": 979634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe6d3fd2003cb8740adc4c3dae035c42565d8bed590f1143cf941495f800db6" } } ], "extra": [ 1, 131, 114, 1, 147, 254, 3, 104, 58, 240, 65, 128, 119, 104, 73, 178, 208, 89, 39, 78, 43, 129, 223, 110, 125, 39, 219, 240, 207, 197, 74, 66, 155, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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