Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac547b362cf45666edb3d655033689beec4787c98fd232157aa788a77e3a2f6

Tx prefix hash: 7f6a70ddbfa04db742daac3579d791b2af3fdf323e3a63cf2cd362fcec7bbb01
Tx public key: 6429717b5de2b673d44b325c0f38859f0b6672adf8b86304ae8fd84dbfed11e9
Timestamp: 1713771389 Timestamp [UCT]: 2024-04-22 07:36:29 Age [y:d:h:m:s]: 00:277:15:59:28
Block: 1005918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198692 RingCT/type: yes/0
Extra: 016429717b5de2b673d44b325c0f38859f0b6672adf8b86304ae8fd84dbfed11e902110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7961697085e5b46b1faa547369445e8cae48f4d7bd47dc8ac3d509c6cb6d2867 0.600000000000 1466768 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": 1005928, "vin": [ { "gen": { "height": 1005918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7961697085e5b46b1faa547369445e8cae48f4d7bd47dc8ac3d509c6cb6d2867" } } ], "extra": [ 1, 100, 41, 113, 123, 93, 226, 182, 115, 212, 75, 50, 92, 15, 56, 133, 159, 11, 102, 114, 173, 248, 184, 99, 4, 174, 143, 216, 77, 191, 237, 17, 233, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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