Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aad6798c325914e23ef8ae91eb4c6b5a2b61fee73f5ff8463111ea2c81ffee5b

Tx prefix hash: b955902716e854e7a1744fba09c1a641754d6d6c4dd700b95571ecf440406d43
Tx public key: 9cea7f3a79106eca5466299cc73bfc5a4cbb4660431d4f0c82cff0a2f236da4b
Timestamp: 1722845630 Timestamp [UCT]: 2024-08-05 08:13:50 Age [y:d:h:m:s]: 00:293:08:50:28
Block: 1081140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209617 RingCT/type: yes/0
Extra: 019cea7f3a79106eca5466299cc73bfc5a4cbb4660431d4f0c82cff0a2f236da4b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 762fcf82f68816c33a7e6f1f76bfe58bcb92fc7c6c268ed93e5d2295077ae42d 0.600000000000 1554771 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": 1081150, "vin": [ { "gen": { "height": 1081140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "762fcf82f68816c33a7e6f1f76bfe58bcb92fc7c6c268ed93e5d2295077ae42d" } } ], "extra": [ 1, 156, 234, 127, 58, 121, 16, 110, 202, 84, 102, 41, 156, 199, 59, 252, 90, 76, 187, 70, 96, 67, 29, 79, 12, 130, 207, 240, 162, 242, 54, 218, 75, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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