Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f5268f4efe7a60c63e0aa346d789cc91d504f1455ceaa5b13e74ce1ec551d47

Tx prefix hash: 84da5311386d35ee5ef5c1f9f997988b72c1aa0f0752241fd6c8b84e0011537e
Tx public key: b0e53e6eee4eecfa63a195172cf00c4c4d61409fc09251afa76ca01533b45fd1
Timestamp: 1727438370 Timestamp [UCT]: 2024-09-27 11:59:30 Age [y:d:h:m:s]: 00:148:08:41:35
Block: 1119226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105796 RingCT/type: yes/0
Extra: 01b0e53e6eee4eecfa63a195172cf00c4c4d61409fc09251afa76ca01533b45fd102110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d24aab00258f04e9c49dd8a9f9fe4ff803b512289086c1155cee09235d513252 0.600000000000 1600707 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": 1119236, "vin": [ { "gen": { "height": 1119226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d24aab00258f04e9c49dd8a9f9fe4ff803b512289086c1155cee09235d513252" } } ], "extra": [ 1, 176, 229, 62, 110, 238, 78, 236, 250, 99, 161, 149, 23, 44, 240, 12, 76, 77, 97, 64, 159, 192, 146, 81, 175, 167, 108, 160, 21, 51, 180, 95, 209, 2, 17, 0, 0, 0, 9, 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