Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bdce358b2a3b66513c50be51264b3c54d280fc1f7a367e9540cad83ccee76a0

Tx prefix hash: 0a31d392a844c5bab8f2d707c191ee0c48bf3a1ea4aa975407a63fe92331d890
Tx public key: f8979ae8e5834e6ff964bfb08f1f2396ca8f692fff63e7ce917f1d8f09cb184d
Timestamp: 1718040865 Timestamp [UCT]: 2024-06-10 17:34:25 Age [y:d:h:m:s]: 00:278:15:59:08
Block: 1041310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199160 RingCT/type: yes/0
Extra: 01f8979ae8e5834e6ff964bfb08f1f2396ca8f692fff63e7ce917f1d8f09cb184d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91a96b67afa4d6257cf8d87bc0efb7c9d68a1ec62491c54a514ce28b2e1f14f7 0.600000000000 1509975 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": 1041320, "vin": [ { "gen": { "height": 1041310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91a96b67afa4d6257cf8d87bc0efb7c9d68a1ec62491c54a514ce28b2e1f14f7" } } ], "extra": [ 1, 248, 151, 154, 232, 229, 131, 78, 111, 249, 100, 191, 176, 143, 31, 35, 150, 202, 143, 105, 47, 255, 99, 231, 206, 145, 127, 29, 143, 9, 203, 24, 77, 2, 17, 0, 0, 0, 2, 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