Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f15f1c47d6d15bbb6b20cef4b172fbe86afe30dac722070781132372ba0b301e

Tx prefix hash: cce8f77bab34a83f6b9da3a846b798b8e39abd008a4c24228bdc34dcecd3cd9b
Tx public key: 57237fefcdf1274cfea93e009e4b73b61d3a13c6684d96b82908ecdb696ce582
Timestamp: 1734187313 Timestamp [UCT]: 2024-12-14 14:41:53 Age [y:d:h:m:s]: 00:189:01:01:18
Block: 1175076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134775 RingCT/type: yes/0
Extra: 0157237fefcdf1274cfea93e009e4b73b61d3a13c6684d96b82908ecdb696ce5820211000000051f0a53eb000000000000000000

1 output(s) for total of 0.605790000000 dcy

stealth address amount amount idx
00: f6d3503a1a60ad935c7cbfa1289f13c71cd16a67ba9f4892f81d4fe61903f61e 0.605790000000 1661307 of 0

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": 1175086, "vin": [ { "gen": { "height": 1175076 } } ], "vout": [ { "amount": 605790000, "target": { "key": "f6d3503a1a60ad935c7cbfa1289f13c71cd16a67ba9f4892f81d4fe61903f61e" } } ], "extra": [ 1, 87, 35, 127, 239, 205, 241, 39, 76, 254, 169, 62, 0, 158, 75, 115, 182, 29, 58, 19, 198, 104, 77, 150, 184, 41, 8, 236, 219, 105, 108, 229, 130, 2, 17, 0, 0, 0, 5, 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