Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 148af4806d626e94a6ebeb9c8576ed92436801c9f5ecd59eb8e3059abee6fd9e

Tx prefix hash: c7874e74346dd07e63b0f128c67f454a51ae4141f73d92bfb537bbfd3922d195
Tx public key: 378b457e0a96e258fdb316ac3aac51c4a6abf6b983ed4a15f0ebe6f7acd1e751
Timestamp: 1724370738 Timestamp [UCT]: 2024-08-22 23:52:18 Age [y:d:h:m:s]: 00:266:23:31:04
Block: 1093807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190677 RingCT/type: yes/0
Extra: 01378b457e0a96e258fdb316ac3aac51c4a6abf6b983ed4a15f0ebe6f7acd1e751021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81a692ecf02704e12aac4fee7b9122df6092b97d0ff2ea478f71a27bb6fa964e 0.600000000000 1568826 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": 1093817, "vin": [ { "gen": { "height": 1093807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81a692ecf02704e12aac4fee7b9122df6092b97d0ff2ea478f71a27bb6fa964e" } } ], "extra": [ 1, 55, 139, 69, 126, 10, 150, 226, 88, 253, 179, 22, 172, 58, 172, 81, 196, 166, 171, 246, 185, 131, 237, 74, 21, 240, 235, 230, 247, 172, 209, 231, 81, 2, 17, 0, 0, 0, 6, 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