Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f03a225d0f0ef1e25d5b732c91d34399d0e02663dd454f04de91453f444e40b0

Tx prefix hash: 77fc670cfa9c8d3b22dc30ac032a5b6454e0a8ae923aae581a1f3981bc6bb6a0
Tx public key: 613c658f9e8832efee02d3d046cbddc1e73e02c1368241d146580866fa49ef2a
Timestamp: 1723843522 Timestamp [UCT]: 2024-08-16 21:25:22 Age [y:d:h:m:s]: 00:232:01:41:25
Block: 1089423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165731 RingCT/type: yes/0
Extra: 01613c658f9e8832efee02d3d046cbddc1e73e02c1368241d146580866fa49ef2a02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06947e37797a1a71b64a389e3ee7a8598e107725f1c0e8c09f52c4a1cb7d7a82 0.600000000000 1564044 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": 1089433, "vin": [ { "gen": { "height": 1089423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06947e37797a1a71b64a389e3ee7a8598e107725f1c0e8c09f52c4a1cb7d7a82" } } ], "extra": [ 1, 97, 60, 101, 143, 158, 136, 50, 239, 238, 2, 211, 208, 70, 203, 221, 193, 231, 62, 2, 193, 54, 130, 65, 209, 70, 88, 8, 102, 250, 73, 239, 42, 2, 17, 0, 0, 0, 13, 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