Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9e3cfe8d62360da1c6b51b0c3b50743fd8544e97fd1d2e822ee122d52085402

Tx prefix hash: c700dd40e7cd9f363857e51caeab8bc1922aec0791909dba0147fb6bd4b0c8e1
Tx public key: 8c36fcbdd5621ff1001775fb8fe2dd0342423839391fc43a591478cb9930f011
Timestamp: 1699226935 Timestamp [UCT]: 2023-11-05 23:28:55 Age [y:d:h:m:s]: 01:084:23:40:17
Block: 885331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321918 RingCT/type: yes/0
Extra: 018c36fcbdd5621ff1001775fb8fe2dd0342423839391fc43a591478cb9930f01102110000000833af99f4000000000000000000

1 output(s) for total of 0.715370264000 dcy

stealth address amount amount idx
00: c55e36cfde7d0a39cd4cfbdd5ae7b0f09a76d3d5851f8c58814c1442964049c0 0.715370264000 1341094 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": 885341, "vin": [ { "gen": { "height": 885331 } } ], "vout": [ { "amount": 715370264, "target": { "key": "c55e36cfde7d0a39cd4cfbdd5ae7b0f09a76d3d5851f8c58814c1442964049c0" } } ], "extra": [ 1, 140, 54, 252, 189, 213, 98, 31, 241, 0, 23, 117, 251, 143, 226, 221, 3, 66, 66, 56, 57, 57, 31, 196, 58, 89, 20, 120, 203, 153, 48, 240, 17, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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