Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc520e5501b299d83a74f4cc37b235e9d5fe3f97c9f2f16e3294ce4c4194f87f

Tx prefix hash: d6f8c7e2b2dfb97141a1691c3805d6005fd5bade5c4042871d276f894d460f75
Tx public key: 151a26fd0ad59de1aa8705b29640fd7066e661e7d7814587d9e75098a8c6d3b1
Timestamp: 1705007880 Timestamp [UCT]: 2024-01-11 21:18:00 Age [y:d:h:m:s]: 01:072:16:07:32
Block: 933240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313041 RingCT/type: yes/0
Extra: 01151a26fd0ad59de1aa8705b29640fd7066e661e7d7814587d9e75098a8c6d3b102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73bdf8ab1aae37afd8a6ee7f0d9a77a309ddf04feb4a5d6b2467ef5a30e77c26 0.600000000000 1391200 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": 933250, "vin": [ { "gen": { "height": 933240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73bdf8ab1aae37afd8a6ee7f0d9a77a309ddf04feb4a5d6b2467ef5a30e77c26" } } ], "extra": [ 1, 21, 26, 38, 253, 10, 213, 157, 225, 170, 135, 5, 178, 150, 64, 253, 112, 102, 230, 97, 231, 215, 129, 69, 135, 217, 231, 80, 152, 168, 198, 211, 177, 2, 17, 0, 0, 0, 3, 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