Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5495e8c0b857d2d2afafb14a550b5085f8d2567a62828742cc28a98b35b07c67

Tx prefix hash: 95919a97325117c55e7d5e25a6cb3aeaaf7912f2c53b62c72203923dc57ebb3c
Tx public key: 8be0d9b3518a6b5c62ce5859631fe23a5bf7e31e2ac0b1dc97d1875f5e8470e7
Timestamp: 1685090280 Timestamp [UCT]: 2023-05-26 08:38:00 Age [y:d:h:m:s]: 01:229:20:03:21
Block: 768385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425686 RingCT/type: yes/0
Extra: 018be0d9b3518a6b5c62ce5859631fe23a5bf7e31e2ac0b1dc97d1875f5e8470e7021100000001e7ace25d000000000000000000

1 output(s) for total of 1.745909385000 dcy

stealth address amount amount idx
00: bfb14bde0e4ee258d0630cd04441256197cd77b0660f8e92438ce6d6da87ed16 1.745909385000 1217580 of 0

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": 768395, "vin": [ { "gen": { "height": 768385 } } ], "vout": [ { "amount": 1745909385, "target": { "key": "bfb14bde0e4ee258d0630cd04441256197cd77b0660f8e92438ce6d6da87ed16" } } ], "extra": [ 1, 139, 224, 217, 179, 81, 138, 107, 92, 98, 206, 88, 89, 99, 31, 226, 58, 91, 247, 227, 30, 42, 192, 177, 220, 151, 209, 135, 95, 94, 132, 112, 231, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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