Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81cef1b25ebea1325d656686eef363f4243a3ffbbef99229bdb25a72e7121516

Tx prefix hash: 77e609ec882f8163c199607b7fecbc7a1a38b2f1146457adb9a34f24649b83e8
Tx public key: f02ae916d0e3cd293483eadbe9bd7570bddb851fde824ccfd18186b1055a33e7
Timestamp: 1718308281 Timestamp [UCT]: 2024-06-13 19:51:21 Age [y:d:h:m:s]: 00:170:15:39:24
Block: 1043533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122142 RingCT/type: yes/0
Extra: 01f02ae916d0e3cd293483eadbe9bd7570bddb851fde824ccfd18186b1055a33e70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c82b23a249519774ba7e679a5553abfd52e5e43fd0754b1df871dc63c34b08a9 0.600000000000 1512686 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": 1043543, "vin": [ { "gen": { "height": 1043533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c82b23a249519774ba7e679a5553abfd52e5e43fd0754b1df871dc63c34b08a9" } } ], "extra": [ 1, 240, 42, 233, 22, 208, 227, 205, 41, 52, 131, 234, 219, 233, 189, 117, 112, 189, 219, 133, 31, 222, 130, 76, 207, 209, 129, 134, 177, 5, 90, 51, 231, 2, 17, 0, 0, 0, 4, 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