Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a580fdf0ad47beb76f090cf0bdd0a9f83b6d913b3573ab600d99473423068741

Tx prefix hash: 5751b87b95582d835a76cbbf698dbf4f4687847f9f9cd7f0af6e62b6750d0b40
Tx public key: 389f98066581d5d252d2960e0abdc7c963a74215d3849b2be051a7402ad9e5e3
Timestamp: 1727874239 Timestamp [UCT]: 2024-10-02 13:03:59 Age [y:d:h:m:s]: 00:020:16:30:28
Block: 1122840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14785 RingCT/type: yes/0
Extra: 01389f98066581d5d252d2960e0abdc7c963a74215d3849b2be051a7402ad9e5e302110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4adf43eb1806b0954590d89391323b66ec84e38010378aa81734048b4c8be0a7 0.600000000000 1605373 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": 1122850, "vin": [ { "gen": { "height": 1122840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4adf43eb1806b0954590d89391323b66ec84e38010378aa81734048b4c8be0a7" } } ], "extra": [ 1, 56, 159, 152, 6, 101, 129, 213, 210, 82, 210, 150, 14, 10, 189, 199, 201, 99, 167, 66, 21, 211, 132, 155, 43, 224, 81, 167, 64, 42, 217, 229, 227, 2, 17, 0, 0, 0, 16, 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