Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7da1773d5e27e4068cca349c37f26b2a2ad9644f0f3338f51f5e5d31e36aee49

Tx prefix hash: 8a735a5cfad5942aa2fcc6772cd2f2e0e6651407cf3897448252705a69c81dba
Tx public key: 56170a8e8c5256ffefa075d1b0a94d37e852eed6b49fc57277f3109349aa3d8b
Timestamp: 1735403651 Timestamp [UCT]: 2024-12-28 16:34:11 Age [y:d:h:m:s]: 00:092:09:01:19
Block: 1185129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65801 RingCT/type: yes/0
Extra: 0156170a8e8c5256ffefa075d1b0a94d37e852eed6b49fc57277f3109349aa3d8b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ef6cd92d4951fb13a45da6b9b644d486932271baa268e91a0dc18e0e69b69a6 0.600000000000 1671594 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": 1185139, "vin": [ { "gen": { "height": 1185129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ef6cd92d4951fb13a45da6b9b644d486932271baa268e91a0dc18e0e69b69a6" } } ], "extra": [ 1, 86, 23, 10, 142, 140, 82, 86, 255, 239, 160, 117, 209, 176, 169, 77, 55, 232, 82, 238, 214, 180, 159, 197, 114, 119, 243, 16, 147, 73, 170, 61, 139, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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