Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aafcda895bafc374b779eb383903dd70fd264fded5e1fba29c4ead237b49833

Tx prefix hash: b8053cd2c4ce65566510d5602e5271b8c063545d9f60a36d069a40baa055f13f
Tx public key: 32d041defdbd6b4aff5af16a43af565fdf51c593caba293f94922b972f701dc3
Timestamp: 1725185791 Timestamp [UCT]: 2024-09-01 10:16:31 Age [y:d:h:m:s]: 00:212:22:50:34
Block: 1100548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152036 RingCT/type: yes/0
Extra: 0132d041defdbd6b4aff5af16a43af565fdf51c593caba293f94922b972f701dc3021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22495e0f841d7d2ff18a23e096cb2c849de41f9f08470a0f6bd7c373c44510db 0.600000000000 1576527 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": 1100558, "vin": [ { "gen": { "height": 1100548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22495e0f841d7d2ff18a23e096cb2c849de41f9f08470a0f6bd7c373c44510db" } } ], "extra": [ 1, 50, 208, 65, 222, 253, 189, 107, 74, 255, 90, 241, 106, 67, 175, 86, 95, 223, 81, 197, 147, 202, 186, 41, 63, 148, 146, 43, 151, 47, 112, 29, 195, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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