Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb7fb02ad416800ac6222d93e1153c774fc3e20b567e445e0e29b2ee31bc3d96

Tx prefix hash: 71e814259ce1476a7ca090bac79a913000cb8ec7fcdb68de38bec01a67038c1f
Tx public key: 65f8a8f997f1934fd8f0f83ee3f37b0467a60f65446ee4c93f6892d5f441ebea
Timestamp: 1713456704 Timestamp [UCT]: 2024-04-18 16:11:44 Age [y:d:h:m:s]: 00:208:18:40:29
Block: 1003292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149474 RingCT/type: yes/0
Extra: 0165f8a8f997f1934fd8f0f83ee3f37b0467a60f65446ee4c93f6892d5f441ebea0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f4d26620ded9932374ae6ea7c2294bae5d17a6d96756959e460b2e0db43b70a 0.600000000000 1463822 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": 1003302, "vin": [ { "gen": { "height": 1003292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f4d26620ded9932374ae6ea7c2294bae5d17a6d96756959e460b2e0db43b70a" } } ], "extra": [ 1, 101, 248, 168, 249, 151, 241, 147, 79, 216, 240, 248, 62, 227, 243, 123, 4, 103, 166, 15, 101, 68, 110, 228, 201, 63, 104, 146, 213, 244, 65, 235, 234, 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