Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cec73aef2b033d10f866cd908dd2f1353b5cda1dd4b7a98763191871cfcf967

Tx prefix hash: ec99a99c657ef9f91167128316ede39be318a849017b7f2a7c3d56d34e99f0f5
Tx public key: 969a67ea63c470e6a3acf33e9ac0aa494416f98fb02524ebc2992a3042508f20
Timestamp: 1700509389 Timestamp [UCT]: 2023-11-20 19:43:09 Age [y:d:h:m:s]: 01:174:19:25:57
Block: 895967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386132 RingCT/type: yes/0
Extra: 01969a67ea63c470e6a3acf33e9ac0aa494416f98fb02524ebc2992a3042508f200211000000014b8f5122000000000000000000

1 output(s) for total of 0.659613271000 dcy

stealth address amount amount idx
00: 5da8ce33677cc52705087c1ae95e9a0cbb51b0b7c6e6c43a49f1d4b7e19dbe3c 0.659613271000 1352218 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": 895977, "vin": [ { "gen": { "height": 895967 } } ], "vout": [ { "amount": 659613271, "target": { "key": "5da8ce33677cc52705087c1ae95e9a0cbb51b0b7c6e6c43a49f1d4b7e19dbe3c" } } ], "extra": [ 1, 150, 154, 103, 234, 99, 196, 112, 230, 163, 172, 243, 62, 154, 192, 170, 73, 68, 22, 249, 143, 176, 37, 36, 235, 194, 153, 42, 48, 66, 80, 143, 32, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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