Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7a1f058782bd8529666ef730b5a22b4decc6e669223135a0bff06a172b4987d

Tx prefix hash: 7bbc0eee48fbc7858e9beab56a499b381efdb010ffb88c34c69ffc96137fe920
Tx public key: 97be28be4eab39091172fc02826bb29d52d4e0e3574e496eae77f21bd0a6b0c8
Timestamp: 1709304207 Timestamp [UCT]: 2024-03-01 14:43:27 Age [y:d:h:m:s]: 01:047:23:51:55
Block: 968891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295314 RingCT/type: yes/0
Extra: 0197be28be4eab39091172fc02826bb29d52d4e0e3574e496eae77f21bd0a6b0c80211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97f6e13aef5988284a9e8b216fc19e87b57444963e3c2ff5ef7c51013d921484 0.600000000000 1428718 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": 968901, "vin": [ { "gen": { "height": 968891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97f6e13aef5988284a9e8b216fc19e87b57444963e3c2ff5ef7c51013d921484" } } ], "extra": [ 1, 151, 190, 40, 190, 78, 171, 57, 9, 17, 114, 252, 2, 130, 107, 178, 157, 82, 212, 224, 227, 87, 78, 73, 110, 174, 119, 242, 27, 208, 166, 176, 200, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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