Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2364bbd20b5f68ba5c13fa870e008cb8a5d623b49f57af81bdc7dbf7183882cc

Tx prefix hash: bf99861cbc315e801791e0dc953a998a6b80bf52fe3c1bac8f6536e93fb2862c
Tx public key: b1cac62a419af0a456502601390b48595987f4ea4adc83d5e92fd575b98c54bb
Timestamp: 1706420569 Timestamp [UCT]: 2024-01-28 05:42:49 Age [y:d:h:m:s]: 00:291:21:52:14
Block: 944953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209022 RingCT/type: yes/0
Extra: 01b1cac62a419af0a456502601390b48595987f4ea4adc83d5e92fd575b98c54bb02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3111817735c96c0fc6a3a95cae1c3bb6497339747f21fa7df9f1214774f19f9 0.600000000000 1403255 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": 944963, "vin": [ { "gen": { "height": 944953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3111817735c96c0fc6a3a95cae1c3bb6497339747f21fa7df9f1214774f19f9" } } ], "extra": [ 1, 177, 202, 198, 42, 65, 154, 240, 164, 86, 80, 38, 1, 57, 11, 72, 89, 89, 135, 244, 234, 74, 220, 131, 213, 233, 47, 213, 117, 185, 140, 84, 187, 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