Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b2ba8e715ba34d7977f25dcb5f4fa54e53dfced984d398335106894d1a79ac2

Tx prefix hash: 59d75c2d2e26d46e99e1da78c0e0636cb7c3ec9324f25b922c84debfc5b6f262
Tx public key: 48847177bd1c2c9bc1b387166069f9a4ba26d5a4ba6d45aad59d0d07a681d972
Timestamp: 1720572175 Timestamp [UCT]: 2024-07-10 00:42:55 Age [y:d:h:m:s]: 00:289:19:00:19
Block: 1062307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207060 RingCT/type: yes/0
Extra: 0148847177bd1c2c9bc1b387166069f9a4ba26d5a4ba6d45aad59d0d07a681d972021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7f6340a2d69a2017c5a2d4c91a1cfb51bb09be885c0b4943ce1bb336ae5debd 0.600000000000 1532808 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": 1062317, "vin": [ { "gen": { "height": 1062307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7f6340a2d69a2017c5a2d4c91a1cfb51bb09be885c0b4943ce1bb336ae5debd" } } ], "extra": [ 1, 72, 132, 113, 119, 189, 28, 44, 155, 193, 179, 135, 22, 96, 105, 249, 164, 186, 38, 213, 164, 186, 109, 69, 170, 213, 157, 13, 7, 166, 129, 217, 114, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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