Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22568931bf9504ccbc51d4a1a1e2beb82f8e4325d1192296b44378f1d012d20b

Tx prefix hash: eeda8dc879b6fb3b59ebb0e723251768acb3a8f841bbbb506fc4d3c1b3918906
Tx public key: ed8086a792e1b5fa984061365c853c15e7d553db26252197c2f89329e5e9efb2
Timestamp: 1737051888 Timestamp [UCT]: 2025-01-16 18:24:48 Age [y:d:h:m:s]: 00:151:23:54:10
Block: 1198775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108338 RingCT/type: yes/0
Extra: 01ed8086a792e1b5fa984061365c853c15e7d553db26252197c2f89329e5e9efb20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9afd0ad6d718aae84c74d79a5b3d476f483864d35d7f301bb4f3ce190e2ee442 0.600000000000 1685402 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": 1198785, "vin": [ { "gen": { "height": 1198775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9afd0ad6d718aae84c74d79a5b3d476f483864d35d7f301bb4f3ce190e2ee442" } } ], "extra": [ 1, 237, 128, 134, 167, 146, 225, 181, 250, 152, 64, 97, 54, 92, 133, 60, 21, 231, 213, 83, 219, 38, 37, 33, 151, 194, 248, 147, 41, 229, 233, 239, 178, 2, 17, 0, 0, 0, 3, 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