Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b84ba6e7ebbea9881d6044f776ac146555837505b09a757acbe61a71b71d34

Tx prefix hash: 7f230a45db647d8b37335959bc24362943ea2896c0522c9d93c0866c945bc56a
Tx public key: d514dc14d3d4ab3b710934e737be4cda3edac3f7a0a0d64eda5a603b27034e27
Timestamp: 1722930591 Timestamp [UCT]: 2024-08-06 07:49:51 Age [y:d:h:m:s]: 00:286:08:38:57
Block: 1081841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204595 RingCT/type: yes/0
Extra: 01d514dc14d3d4ab3b710934e737be4cda3edac3f7a0a0d64eda5a603b27034e27021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5f161793fccd1e66c9e65bfe2b7d451e00502bc71b210a77635d5842b00d201 0.600000000000 1555664 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": 1081851, "vin": [ { "gen": { "height": 1081841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5f161793fccd1e66c9e65bfe2b7d451e00502bc71b210a77635d5842b00d201" } } ], "extra": [ 1, 213, 20, 220, 20, 211, 212, 171, 59, 113, 9, 52, 231, 55, 190, 76, 218, 62, 218, 195, 247, 160, 160, 214, 78, 218, 90, 96, 59, 39, 3, 78, 39, 2, 17, 0, 0, 0, 2, 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