Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f77fdfe2a7202697594187b16bf9ef2df4a45b66a702d51dac6eaf90429c40d6

Tx prefix hash: 45fcb579fa56e493bc46f9af09652695b4358ac4a1c1fe4f3d9fdca0869ba586
Tx public key: fa6b4a7c842fa0cb5e86d4529ad323c6119fe61a77e47801c97cf55a3a3a54ad
Timestamp: 1720200204 Timestamp [UCT]: 2024-07-05 17:23:24 Age [y:d:h:m:s]: 00:190:00:11:22
Block: 1059208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135966 RingCT/type: yes/0
Extra: 01fa6b4a7c842fa0cb5e86d4529ad323c6119fe61a77e47801c97cf55a3a3a54ad0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6591264899d0aa4eee648f119eab61bf2442e62c3fee617dda67a66f55d0f4de 0.600000000000 1529673 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": 1059218, "vin": [ { "gen": { "height": 1059208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6591264899d0aa4eee648f119eab61bf2442e62c3fee617dda67a66f55d0f4de" } } ], "extra": [ 1, 250, 107, 74, 124, 132, 47, 160, 203, 94, 134, 212, 82, 154, 211, 35, 198, 17, 159, 230, 26, 119, 228, 120, 1, 201, 124, 245, 90, 58, 58, 84, 173, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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