Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86674f0d930e19aa65f6a69672e0d5ba1c871ba200f4f7ad6742bb37468503e7

Tx prefix hash: 2941ef430fb57237ce3a384a3afc7f20bb628e40e8ffbe471b889e6279a3263f
Tx public key: c0abb660bd7b4fac3f89e346ba00ccef4e488134631b867821e7fe3268bce1c0
Timestamp: 1706551551 Timestamp [UCT]: 2024-01-29 18:05:51 Age [y:d:h:m:s]: 01:308:23:58:09
Block: 946038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479685 RingCT/type: yes/0
Extra: 01c0abb660bd7b4fac3f89e346ba00ccef4e488134631b867821e7fe3268bce1c002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c4cf9167d216512c346da059f1f168f48f6d64b427b7fd1d54719d91c6096a7 0.600000000000 1404368 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": 946048, "vin": [ { "gen": { "height": 946038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c4cf9167d216512c346da059f1f168f48f6d64b427b7fd1d54719d91c6096a7" } } ], "extra": [ 1, 192, 171, 182, 96, 189, 123, 79, 172, 63, 137, 227, 70, 186, 0, 204, 239, 78, 72, 129, 52, 99, 27, 134, 120, 33, 231, 254, 50, 104, 188, 225, 192, 2, 17, 0, 0, 0, 7, 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